LA County RRCC · Case Study · Sam Deo
Home›Products›Case study
Case study 06 · LA County RRCC · lavote.gov

A redesign was already in motion. I was asked what I would do differently

I was a designer on lavote.gov. The developers had a redesign direction in mind and my manager asked for my read on it. So I answered with a full proposal: an information architecture for the whole site, and five templates that show it working. The structural and content work I put forward was adopted; the design below is the proposal it came from.

Client projectInformation architectureContent strategyDesign proposal · 5 templates
My proposed homepage: a five-section navigation, a persistent election bar with the countdown and ballot-tracking links, a navy VOTE hero, and an eight-tile Most Requested grid above the three service lines. What shipped: a four-item nav — Services, Newsroom, About Us, Contact — with search and a single English language control, a photographic hero carousel reading “Marriage License · Getting married? Apply for a marriage license.”, and three icon-led entry cards for Voting and Elections, Records and County Clerk.
What shipped
My proposal
Drag the handle, or focus it and use the arrow keys. Left is what shipped. Right is my proposal, which keeps the same three service lines but puts the eight things residents actually come to do above them.
Role
Designer · information architecture and cross-site patterns
The ask
Asked by my manager for a perspective on the redesign direction the developers had in mind
What I gave back
A site-wide IA, five designed templates, and the design system underneath them
TL;DR
Problem
A redesign with no structure
lavote.gov served 10 million residents, and nothing had ever been removed from its navigation.
What I did
A proposal, not a critique
Five sections, a two-click depth cap, and naming rules for every page.
Result
The navigation was adopted
Plus five templates and an accessibility review for the team.
01 · My role

My role: answer with a structure

I was one of the designers on lavote.gov, working at page and pattern level. The dev team already had a redesign in motion and I was asked what I'd do differently.

What actually reached production was the homepage grouping. Everything else here is the pitch. The “What changed” table marks which is which, row by row.

02 · The problem

A redesign with no structure

I was one of the designers on lavote.gov, working page and pattern level.

The honest answer was that the disagreement was not about the surface. Re-skinning the homepage would have preserved the thing making it hard to use.

02 · The problem, in evidence

Nothing had ever been removed

Working across the site meant auditing it constantly, and what that kept producing was structural evidence: years of pages, forms and links added without a structure to absorb them, under a visual system that had fallen behind the county's other digital properties.

The homepage alone routed to a sixteen-button “Top Requests” grid sitting on top of a seven-tab primary nav. For a site that has to serve a first-time voter and someone requesting a decades-old marriage record with equal clarity, that density made the first decision the hardest one.

Nothing on that page was there by accident. Every button existed because someone, at some point, needed exactly that link, which is precisely why it had never been cut.

16+
buttons in the “Top Requests” grid
7
flat tabs in the primary nav
3
service areas the whole site actually divides into
16
languages the structure has to hold, up from 9
03 · What I decided

Three moves that decide where content lives

The department is one brand with three service lines, and the site had never been organised around them. That is the spine of the proposal: sections that match how the department actually works, a navigation built to hold the long tail, and landings that rank tasks instead of listing them.

None of these moves reduce what the site can do. They shift the burden off the homepage and onto the navigation and the section landings, which were built for it.

Standardising labels sounds like housekeeping, and it was the change that made any of it possible: you cannot group services into sections while the same service answers to three different names. Cutting redundant pages and rewriting legalese into plain language came with it.

NavigationAdopted
Seven flat tabs became five sections with mega-menus
Voting, Elections, Recorder, County Clerk, Get Involved. The department's own organising logic, with the long tail of each one hanging off a mega-menu instead of a homepage grid.
HomepageProposed
Sixteen buttons became eight tasks, then three doors
Eight things residents actually arrive to do, register, track a ballot, request a birth record, apply for a marriage license, sit above the three service lines. The undifferentiated grid becomes two ranked decisions instead of one flat one.
Election barProposed
Election information left the homepage and went sitewide
A persistent bar under the masthead carries the countdown, the next election date, ballot tracking and registration status on every page. So a resident who lands deep in Recorder still knows an election is coming.
The fixed point
Our Services was not up for discussion

The developers had built the Our Services module and were proud of it, and removing it was never on the table. So the proposal keeps it: the three service lines survive intact on every template. The eight most-requested tasks sit above it rather than replacing it, which turned out to be the better argument anyway: Our Services answers which part of the department, and the task tiles answer what am I here to do. Designing around the constraint separated two questions the old grid had collapsed into one.

04 · What shipped, what I proposed

Five templates, one structure

A homepage on its own proves nothing. The question was whether the three service lines hold up as a way to organise the whole site.

lavote.gov · proposed
{{ shot.title }}

{{ shot.desc }}

Scroll inside the frame to see each page in full.
04 · The sitemap underneath

Five sections, three levels

The templates only work if the map behind them does. The department is one brand with three service lines, so the map starts there.

Depth is capped at three levels. Anything that would sit at level four is a task, not a page, and belongs in the mega-menu or the accordion at the foot of its landing.

Voting
How to cast a ballot
  • Vote by Mail
  • Voting in Person
  • Interactive Sample Ballot
  • Mobile Vote Center
  • Flex Program
  • Military & Overseas
  • Voting Accessibility
Elections
What is on the ballot, and how it is counted
  • Current & Upcoming Elections
  • Find My Election Information
  • Election Results
  • Certifying Results
  • Public Observation
  • Candidate & Measure Filing
  • Election Resources
Recorder
Records the county holds
  • Birth Records
  • Death Records
  • Marriage Records
  • Property Document Recording
  • Real Estate Records
  • Military Discharge
  • UCC Financing Statements
County Clerk
Licenses, filings and registrations
  • Marriage Licenses & Ceremonies
  • Fictitious Business Names
  • Notary Public Oath & Bond
  • Domestic Partnerships
  • Professional Registrations
  • Translation & Authentication
  • Environmental Notices & Fees
Get Involved
Working an election, not voting in one
  • Become an Election Worker
  • Community & Voter Outreach
  • Voter Education
  • Do Business with Us
  • Volunteer Programs
A page earns its place by being a destination
If a link only exists to reach one other link, it is a menu item, not a page. That single rule removed most of the redundancy the audit had been finding for months.
Verbs for tasks, nouns for information
Request a Birth Record, Apply for a Marriage License, File a Fictitious Business Name: anything actionable opens with a verb. General Info, Fees and Eligibility stay nouns, so a resident can tell the two apart before clicking.
One name per service, everywhere
The same service was answering to three different names across the site. Fixing that is what made grouping possible at all.
05 · What changed

Before and after

Every row below is a structural claim the five templates make. The grouping is in production; the rest is what I put forward.

 Live siteProposed
Primary nav7 flat tabs5 sections with mega-menus
Homepage requests16-button grid8 most-requested tasks, then 3 service lines
Election informationScattered across pagesPersistent election bar, sitewide
Long tailFlat link listsAccordion browse at the foot of each landing
06 · Appendix: the design system

Four colors, one typeface

A deck settles what a brand looks like, not how it gets built, and a concept is only an argument until someone can build the next page from it. The department had a 2020 brand deck and a live site, but nothing in between.

The hardest part was not picking values. It was writing down proportion: white dominates, navy carries structure, light blue carries interaction, yellow is a spark.

Read the full brand kit →
Color · proportion
#FCC227
Spark: CTAs, rules, numerals
#2DAAE7
Interaction: links, icon chips
#213F80
Structure: headings, footer
#FFFFFF
Ground: the majority of any page
Target proportion on a typical page. White 62 · navy 24 · blue 10 · yellow 4
Type · one family
Clear Sans
Bold · Regular · Book. No serif, no display face: hierarchy comes from size, weight and color only.
Heading Marriage Licenses
Body 17px / 1.6, measure capped near 66ch: procedural copy people read carefully.
Micro County Clerk · eyebrow
Components · specimen
Button · md
Register to Vote View Options Fees
IconChip · the brand's core device
Icon - Registrar of Voters Icon - Recorder Icon - County Clerk A pale blue circle holding the department's own flat illustrations
Badge · neutral · accent · success
Press Release Election Day Filed
SectionCard · hover state
Icon - Marriage Licenses
Marriage Licenses
Apply for a marriage license, book a civil ceremony, or request a copy of a certificate
Learn More
Alert · warning · inline
Ballots are in the mail
Vote by Mail ballots were mailed to all registered voters beginning October 7.
Twenty-two components in four groups, core, forms, navigation, content, each one traced to a surface that already existed on the site rather than invented. Three were consolidations I flagged as additions: IconChip, Callout, Badge.
The 2020 LA County RRCC Branding Guidelines, eight spreads: the cover, The Brand, Retained Logo Guidelines, Color Harmony with the four hex values, Font Selection showing Clear Sans in Bold, Regular and Book, Imagery and Iconography, Communication Style, and Branding Across Platforms.
The 2020 Branding Guidelines. The authoritative source for the four colors, the typeface, the logo policy and the tone of voice.
Read the accessibility review → Visit lavote.gov ↗ Back to all products

More work

Products →
LA County Registrar-Recorder/County Clerk: a team project. My manager asked for my perspective on the redesign direction the developers had in mind; the five templates, the information architecture and the design system here are the proposal I gave back. The structural and content work was adopted into the live site; the templates are a proposal and were not shipped as designed. The "legacy" and "what shipped" screenshots are of the public site; the wireframe and the templates are my own work, recreated for this case study.